CCSAAS-2663: Get credential flow for ACCS REST API #459
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jeff-matthews
added
enhancement
|
As discussed with the team during our DocTechTalk today, I'm going to open a separate PR with the simplified, phase 1 approach (hardcoded) to expedite testing. I'll keep this draft open for reference when we're ready for phase 2 (env vars). |
4 tasks
|
No need to keep this open for reference. |
github-project-automation
bot
moved this from 📋 Needs Review
to 🏁 Done
in Commerce - Pull Requests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
This pull request (PR) implements the GetCredential component for the Adobe Commerce as a Cloud Service REST API.
It's based mostly on the AEP implementation, but matches directory and JS file name in upstream repo example (AdobeDocs/adobe-dev-console#140).
The build will probably fail until we have template IDs.
Note
I'm not sure if the
RedoclyAPIBlock>component will work the way that we want it to until I deploy to staging. I don't want to deploy to staging until the Developer Console team creates the project template that I requested in CCSAAS-2663.TODOs
template_idimplementation (see Slack)RedoclyAPIBlockperformance; will probably need to revert to hosted schema for performance.Staging
blocked
whastnew
Enabled a workflow to allow users to get credentials to try the Adobe Commerce as a Cloud Service REST API directly from the reference documentation.